feat(interlink): console doc for private beta #4319
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-authored-by: Benedikt Rollik <[email protected]>
Co-authored-by: Benedikt Rollik <[email protected]>
Co-authored-by: Benedikt Rollik <[email protected]>
Co-authored-by: Benedikt Rollik <[email protected]>
Co-authored-by: nerda-codes <[email protected]>
Co-authored-by: nerda-codes <[email protected]>
RoRoJ
added
the
do not merge
RoRoJ
added
status: doc review
bene2k1
approved these changes
Jan 30, 2025
|
|
||
| After you have [ordered your InterLink](/interlink/how-to/order-interlink), further action is required on both the customer side and the [partner](/interlink/concepts/#partner) side before the InterLink is provisioned and ready for active use. This page walks you through the steps to take and how to deal with potential problems that could arise. | ||
|
|
||
| <Lightbox src="scaleway-interlink-ordering.webp" alt="A four step flow chart shows the following steps: 1. User orders InterLink via Scaleway, 2. User requests InterLink from partner, 3. Partner accepts InterLink request, 4. Partner provisions InterLink." /> |
There was a problem hiding this comment.
Suggested change
| <Lightbox src="scaleway-interlink-ordering.webp" alt="A four step flow chart shows the following steps: 1. User orders InterLink via Scaleway, 2. User requests InterLink from partner, 3. Partner accepts InterLink request, 4. Partner provisions InterLink." /> | |
| <Lightbox src="scaleway-interlink-ordering.webp" alt="A four-step flow chart shows the following steps: 1. User orders InterLink via Scaleway, 2. User requests InterLink from partner, 3. Partner accepts InterLink request, 4. Partner provisions InterLink." /> |
|
|
||
| 2. Click on the InterLink that you want to finish provisioning. The InterLink's **Overview** page displays. | ||
|
|
||
| <Lightbox src="scaleway-interlink-overview-requesting.webp" alt="A screen in the Scaleway console show's an overview of an InterLink's partner, location, region, bandwidth, creation date, pairing key, and IPv4/IPv6 connectivity status." /> |
There was a problem hiding this comment.
Suggested change
| <Lightbox src="scaleway-interlink-overview-requesting.webp" alt="A screen in the Scaleway console show's an overview of an InterLink's partner, location, region, bandwidth, creation date, pairing key, and IPv4/IPv6 connectivity status." /> | |
| <Lightbox src="scaleway-interlink-overview-requesting.webp" alt="A screen in the Scaleway console shows an overview of an InterLink's partner, location, region, bandwidth, creation date, pairing key, and IPv4/IPv6 connectivity status." /> |
|
|
||
| ## Wait for partner to accept InterLink request | ||
|
|
||
| Once you have requested the InterLink from your partner, you must wait for them to respond to your request. There is no further action for you to take at this point. You can keep track of your InterLink's [status](/interlink/reference-content/statuses/) via the [InterLink listing](https://console.scaleway.com/interlink/links) in the Scaleway console. |
There was a problem hiding this comment.
Suggested change
| Once you have requested the InterLink from your partner, you must wait for them to respond to your request. There is no further action for you to take at this point. You can keep track of your InterLink's [status](/interlink/reference-content/statuses/) via the [InterLink listing](https://console.scaleway.com/interlink/links) in the Scaleway console. | |
| Once you have requested the InterLink from your partner, you must wait for them to respond to your request. There is no further action for you to take at this point. You can keep track of your InterLink's [status](/interlink/reference-content/statuses/) via the [InterLink listing](https://console.scaleway.com/interlink/links) in the Scaleway console. |
|
|
||
| ## Partner provisions InterLink | ||
|
|
||
| When the partner has finished provisioning your InterLink, it moves to `Active` status. This indicates that the physical link and necessary accompanying configuration has been completed on the partner's side, and your InterLink is ready for use. |
There was a problem hiding this comment.
Suggested change
| When the partner has finished provisioning your InterLink, it moves to `Active` status. This indicates that the physical link and necessary accompanying configuration has been completed on the partner's side, and your InterLink is ready for use. | |
| When the partner has finished provisioning your InterLink, it moves to `Active` status. This indicates that the physical link and necessary accompanying configuration have been completed on the partner's side, and your InterLink is ready for use. |
|
|
||
| <Lightbox src="scaleway-interlink-attach-vpc.webp" alt="A screen in the Scaleway console invites the user to attach a VPC to complete the connection from their external infrastructure, across the InterLink to their Scaleway resources. A dropdown menu allows a VPC to be selected. A banner reminds users to check any attached route filter lists for compatibility with the selected VPC." /> | ||
|
|
||
| 4. Select one of your existing VPCs from the dropdown list. It must be in the same region as the InterLink. Alternatively, click **+ Create VPC** to create and attach a new VPC. |
There was a problem hiding this comment.
Suggested change
| 4. Select one of your existing VPCs from the dropdown list. It must be in the same region as the InterLink. Alternatively, click **+ Create VPC** to create and attach a new VPC. | |
| 6. Select one of your existing VPCs from the dropdown list. It must be in the same region as the InterLink. Alternatively, click **+ Create VPC** to create and attach a new VPC. |
| Ensure that the allowed routes list that is attached to the InterLink is suitable for the VPC you are attaching. Remember that the outgoing routes in the list should correspond to the route announcements to whitelist from the VPC itself. | ||
| </Message> | ||
|
|
||
| 5. Click **Attach VPC** |
There was a problem hiding this comment.
Suggested change
| 5. Click **Attach VPC** | |
| 7. Click **Attach VPC**. |
Comment on lines
+209
to
+214
|
|
||
|
|
||
|
|
||
|
|
||
|
|
||
|
|
| - Create and attach an allowed routes list | ||
| - Activate route propagation | ||
|
|
||
| <Lightbox src="scaleway-interlink-config.webp" alt="A four step flow chart shows the following steps: 1. Create InterLink, 2. Attach VPC, 3. Attach allowed routes list, 4. Activate route propagation. After these steps are complete, traffic can flow across the InterLink" /> |
There was a problem hiding this comment.
Suggested change
| <Lightbox src="scaleway-interlink-config.webp" alt="A four step flow chart shows the following steps: 1. Create InterLink, 2. Attach VPC, 3. Attach allowed routes list, 4. Activate route propagation. After these steps are complete, traffic can flow across the InterLink" /> | |
| <Lightbox src="scaleway-interlink-config.webp" alt="A four-step flow chart shows the following steps: 1. Create InterLink, 2. Attach VPC, 3. Attach allowed routes list, 4. Activate route propagation. After these steps are complete, traffic can flow across the InterLink" /> |
|
|
||
| 2. Click on the InterLink that you want to configure. The InterLink's **Overview** page displays. | ||
|
|
||
| <Lightbox src="scaleway-interlink-overview-up.webp" alt="A screen in the Scaleway console show's an overview of an InterLink's partner, location, region, bandwidth, creation date, pairing key, and IPv4/IPv6 connectivity status. Underneath are the 'Attached VPC', 'Route propagation' and 'Tags' panels." /> |
There was a problem hiding this comment.
Suggested change
| <Lightbox src="scaleway-interlink-overview-up.webp" alt="A screen in the Scaleway console show's an overview of an InterLink's partner, location, region, bandwidth, creation date, pairing key, and IPv4/IPv6 connectivity status. Underneath are the 'Attached VPC', 'Route propagation' and 'Tags' panels." /> | |
| <Lightbox src="scaleway-interlink-overview-up.webp" alt="A screen in the Scaleway console shows an overview of an InterLink's partner, location, region, bandwidth, creation date, pairing key, and IPv4/IPv6 connectivity status. Underneath are the 'Attached VPC', 'Route propagation' and 'Tags' panels." /> |
| 1. Click **InterLink** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu. A listing of your InterLinks displays. | ||
|
|
||
| 2. Click on the InterLink that you want to configure. The InterLink's **Overview** page displays. | ||
| <Lightbox src="scaleway-interlink-overview-up.webp" alt="A screen in the Scaleway console show's an overview of an InterLink's partner, location, region, bandwidth, creation date, pairing key, and IPv4/IPv6 connectivity status. Underneath are the 'Attached VPC', 'Route propagation' and 'Tags' panels." /> |
There was a problem hiding this comment.
Suggested change
| <Lightbox src="scaleway-interlink-overview-up.webp" alt="A screen in the Scaleway console show's an overview of an InterLink's partner, location, region, bandwidth, creation date, pairing key, and IPv4/IPv6 connectivity status. Underneath are the 'Attached VPC', 'Route propagation' and 'Tags' panels." /> | |
| <Lightbox src="scaleway-interlink-overview-up.webp" alt="A screen in the Scaleway console shows an overview of an InterLink's partner, location, region, bandwidth, creation date, pairing key, and IPv4/IPv6 connectivity status. Underneath are the 'Attached VPC', 'Route propagation' and 'Tags' panels." /> |
|
|
||
| 2. Click on the InterLink that you want to configure. The InterLink's **Overview** page displays. | ||
|
|
||
| <Lightbox src="scaleway-interlink-overview-up.webp" alt="A screen in the Scaleway console show's an overview of an InterLink's partner, location, region, bandwidth, creation date, pairing key, and IPv4/IPv6 connectivity status. Underneath are the 'Attached VPC', 'Route propagation' and 'Tags' panels." /> |
There was a problem hiding this comment.
Suggested change
| <Lightbox src="scaleway-interlink-overview-up.webp" alt="A screen in the Scaleway console show's an overview of an InterLink's partner, location, region, bandwidth, creation date, pairing key, and IPv4/IPv6 connectivity status. Underneath are the 'Attached VPC', 'Route propagation' and 'Tags' panels." /> | |
| <Lightbox src="scaleway-interlink-overview-up.webp" alt="A screen in the Scaleway console shows an overview of an InterLink's partner, location, region, bandwidth, creation date, pairing key, and IPv4/IPv6 connectivity status. Underneath are the 'Attached VPC', 'Route propagation' and 'Tags' panels." /> |
| If route propagation was activated, it will be automatically deactivated when you detach the VPC. | ||
| </Message> | ||
|
|
||
| 4. Click **Detach VPC** |
There was a problem hiding this comment.
Suggested change
| 4. Click **Detach VPC** | |
| 4. Click **Detach VPC**. |
| <Message type="tip"> | ||
| Routes within these destinations will be propagated, allowing traffic from your external infrastructure to be routed via InterLink to your VPC. For example, adding `172.16.4.0/22` whitelists all 1,024 IPs in this block, from `172.16.4.0` to `172.16.7.255`. | ||
|
|
||
| IPv4 and IPv6 routes must be defined separately.. |
There was a problem hiding this comment.
Suggested change
| IPv4 and IPv6 routes must be defined separately.. | |
| IPv4 and IPv6 routes must be defined separately. |
|
|
||
| 2. Click on the InterLink that you want to delete. The InterLink's **Overview** page displays. | ||
|
|
||
| <Lightbox src="scaleway-interlink-overview-up.webp" alt="A screen in the Scaleway console show's an overview of an InterLink's partner, location, region, bandwidth, creation date, pairing key, and IPv4/IPv6 connectivity status. Underneath are the 'Attached VPC', 'Route propagation' and 'Tags' panels." /> |
There was a problem hiding this comment.
Suggested change
| <Lightbox src="scaleway-interlink-overview-up.webp" alt="A screen in the Scaleway console show's an overview of an InterLink's partner, location, region, bandwidth, creation date, pairing key, and IPv4/IPv6 connectivity status. Underneath are the 'Attached VPC', 'Route propagation' and 'Tags' panels." /> | |
| <Lightbox src="scaleway-interlink-overview-up.webp" alt="A screen in the Scaleway console shows an overview of an InterLink's partner, location, region, bandwidth, creation date, pairing key, and IPv4/IPv6 connectivity status. Underneath are the 'Attached VPC', 'Route propagation' and 'Tags' panels." /> |
|
|
||
| 5. Choose a [region](/interlink/concepts/#partner) for your InterLink. This must correspond to the Scaleway VPC you want to attach later. | ||
|
|
||
| 6. Choose a [location](/interlink/concepts/#partner) for your InterLink. This represents the physical location where the connection to Scaleway's network will be established. |
There was a problem hiding this comment.
Suggested change
| 6. Choose a [location](/interlink/concepts/#partner) for your InterLink. This represents the physical location where the connection to Scaleway's network will be established. | |
| 6. Choose a [location](/interlink/concepts/#location) for your InterLink. This represents the physical location where the connection to Scaleway's network will be established. |
|
|
||
| 4. Select a [partner](/interlink/concepts/#partner). To establish an InterLink connection via a partner, generally you must be client of that partner, e.g. with your infrastructure in their datacenter, or on your own premises using the partner as a network provider. [Get help with choosing a partner](/interlink/reference-content/overview/#hosted-interlinks). | ||
|
|
||
| 5. Choose a [region](/interlink/concepts/#partner) for your InterLink. This must correspond to the Scaleway VPC you want to attach later. |
There was a problem hiding this comment.
Suggested change
| 5. Choose a [region](/interlink/concepts/#partner) for your InterLink. This must correspond to the Scaleway VPC you want to attach later. | |
| 5. Choose a [region](/interlink/concepts/#region) for your InterLink. This must correspond to the Scaleway VPC you want to attach later. |
|
|
||
| 2. Click on the InterLink that you want to configure. The InterLink's **Overview** page displays. | ||
|
|
||
| <Lightbox src="scaleway-interlink-overview-up.webp" alt="A screen in the Scaleway console show's an overview of an InterLink's partner, location, region, bandwidth, creation date, pairing key, and IPv4/IPv6 connectivity status. Underneath are the 'Attached VPC', 'Route propagation' and 'Tags' panels." /> |
There was a problem hiding this comment.
Suggested change
| <Lightbox src="scaleway-interlink-overview-up.webp" alt="A screen in the Scaleway console show's an overview of an InterLink's partner, location, region, bandwidth, creation date, pairing key, and IPv4/IPv6 connectivity status. Underneath are the 'Attached VPC', 'Route propagation' and 'Tags' panels." /> | |
| <Lightbox src="scaleway-interlink-overview-up.webp" alt="A screen in the Scaleway console shows an overview of an InterLink's partner, location, region, bandwidth, creation date, pairing key, and IPv4/IPv6 connectivity status. Underneath are the 'Attached VPC', 'Route propagation' and 'Tags' panels." /> |
|
|
||
| 3. Select a [connection type](/interlink/concepts/#connection-type), the type of physical InterLink connection. For now, only **hosted** connections are available. | ||
|
|
||
| 4. Select a [partner](/interlink/concepts/#partner) to facilitate the physical connection between the external infrastructure and the Scaleway VPC. Generally you must be client of the chosen partner, e.g. with your infrastructure in their datacenter, or on your own premises using the partner as a network provider. [Get help with choosing a partner](/interlink/reference-content/overview/#hosted-interlinks). |
There was a problem hiding this comment.
Suggested change
| 4. Select a [partner](/interlink/concepts/#partner) to facilitate the physical connection between the external infrastructure and the Scaleway VPC. Generally you must be client of the chosen partner, e.g. with your infrastructure in their datacenter, or on your own premises using the partner as a network provider. [Get help with choosing a partner](/interlink/reference-content/overview/#hosted-interlinks). | |
| 4. Select a [partner](/interlink/concepts/#partner) to facilitate the physical connection between the external infrastructure and the Scaleway VPC. Generally, you must be client of the chosen partner, e.g. with your infrastructure in their datacenter, or on your own premises using the partner as a network provider. [Get help with choosing a partner](/interlink/reference-content/overview/#hosted-interlinks). |
|
|
||
| 4. Select a [partner](/interlink/concepts/#partner) to facilitate the physical connection between the external infrastructure and the Scaleway VPC. Generally you must be client of the chosen partner, e.g. with your infrastructure in their datacenter, or on your own premises using the partner as a network provider. [Get help with choosing a partner](/interlink/reference-content/overview/#hosted-interlinks). | ||
|
|
||
| 5. Choose a [region](/interlink/concepts/#partner) for your InterLink. This must correspond to the Scaleway VPC you want to attach later. |
There was a problem hiding this comment.
Suggested change
| 5. Choose a [region](/interlink/concepts/#partner) for your InterLink. This must correspond to the Scaleway VPC you want to attach later. | |
| 5. Choose a [region](/interlink/concepts/#region) for your InterLink. This must correspond to the Scaleway VPC you want to attach later. |
|
|
||
| 5. Choose a [region](/interlink/concepts/#partner) for your InterLink. This must correspond to the Scaleway VPC you want to attach later. | ||
|
|
||
| 6. Choose a [location](/interlink/concepts/#partner) for your InterLink. This represents the physical location where the connection to Scaleway's network will be established. |
There was a problem hiding this comment.
Suggested change
| 6. Choose a [location](/interlink/concepts/#partner) for your InterLink. This represents the physical location where the connection to Scaleway's network will be established. | |
| 6. Choose a [location](/interlink/concepts/#location) for your InterLink. This represents the physical location where the connection to Scaleway's network will be established. |
|
|
||
| 3. In the **Route propagation** section, use the toggle <Icon name="toggle" /> to turn route propagation **ON**. | ||
|
|
||
| A pop-up displays, showing the attached allowed routes list which will define the incoming and outgoing route announcements to accept. You can change the attached allowed routes list if you wish. |
There was a problem hiding this comment.
Suggested change
| A pop-up displays, showing the attached allowed routes list which will define the incoming and outgoing route announcements to accept. You can change the attached allowed routes list if you wish. | |
| A pop-up displays, showing the attached allowed routes list which will define the incoming and outgoing route announcements to accept. You can change the attached allowed routes list if you wish. |
|
|
||
| 5. Type **DELETE** in the box, and click **Delete InterLink**. | ||
|
|
||
| You are returned to the InterLink's **Overview** page, where it's status now shows as **Deprovisioning**. Scaleway stops billing you for your InterLink at this point, and it can no longer be configured, un-deleted, or used to route traffic. |
There was a problem hiding this comment.
Suggested change
| You are returned to the InterLink's **Overview** page, where it's status now shows as **Deprovisioning**. Scaleway stops billing you for your InterLink at this point, and it can no longer be configured, un-deleted, or used to route traffic. | |
| You are returned to the InterLink's **Overview** page, where its status now shows as **Deprovisioning**. Scaleway stops billing you for your InterLink at this point, and it can no longer be configured, un-deleted, or used to route traffic. |
|
|
||
| 5. Type **DELETE** in the box, and click **Delete InterLink**. | ||
|
|
||
| You are returned to the InterLink's **Overview** page, where it's status now shows as **Deprovisioning**. Scaleway stops billing you for your InterLink at this point, and it can no longer be configured, un-deleted, or used to route traffic. |
There was a problem hiding this comment.
Suggested change
| You are returned to the InterLink's **Overview** page, where it's status now shows as **Deprovisioning**. Scaleway stops billing you for your InterLink at this point, and it can no longer be configured, un-deleted, or used to route traffic. | |
| You are returned to the InterLink's **Overview** page, where its status now shows as **Deprovisioning**. Scaleway stops billing you for your InterLink at this point, and it can no longer be configured, un-deleted, or used to route traffic. |
jcirinosclwy
approved these changes
Feb 24, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Publish console documentation (how-tos and quickstart) for InterLink, which will still be in private beta (so not in menu and no FAQ yet).